Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference


Client database connection parameters

Use the parameters listed in Table 3–8 to control how you connect to a specified database.

If you use the Physical Database Name (-db) parameter to specify more than one database when you start a session, specify the connection parameters for each database after the database name to which they apply and before the next -db parameter. OpenEdge applies database connection parameters only to the previously specified database. For example:

mpro [ -db] db1-name [ db1-parameters ] -db db2-name [ db2-parameters ] 

Note: OpenEdge implicitly specifies the -db parameter for the first database.

You can specify all other parameters anywhere on the command line. If you specify the same parameter more than once, OpenEdge uses the value you provide for the last instance of the parameter.

Table 3–8: Client database connection parameters
Syntax
Parameter
Purpose
-1 
Single-user mode1
Start OpenEdge in single-user mode.
-B n 
Blocks in database buffers1
Specify the number of database buffer blocks.
-Bp n 
Private read-only buffers
Request a number of private read-only buffers.
-brl 
Bleeding record lock
Hold a share lock on a released record used by more than one buffer.
-cache filename 
Schema cache file
Read the database schema from a local file instead of the database.
-cp { com-parms | 
filename } 
Communications parameter file
Override preset connection parameters for auto-connect databases.
-cs n 
Cursor size
Change the maximum number of index levels.
-db physical-dbname 
Physical database name
Identify one or more databases to connect to at startup.
-DataService 
data-service 
DataService
Connect through a NameServer to an ODBC or ORACLE DataServer.
-directio 
Direct I/O1,2
Open all files in unbuffered mode.
-dt db-type 
Database type
Identify the database type.
-F 
Force access
Allow access to a damaged database. Call Technical Support before using -F.
TCP: -H host-name 
SNA: PLU= plu-name 
Host name
Identify a remote host.
-hash n 
Hast table entries1
Specify the number of hash table entries for the buffer pool.
-i 
No crash protection1
Run OpenEdge without database integrity or recovery.
-is  
AS/400 ignore stamp
Stop a client from comparing time stamps when connection to an AS/400 database.
-ld logical-dbname 
Logical database name
Assign the logical database name.
-MF n 
Delayed BI file write1, 2
Delay writing the last before-image (BI) file records.
-Mm n 
Message buffer size.
Specify the message buffer size for network client/server protocols.
-nohostverify 
No Host Verify
Turns off host verification for a Secure Sockets Layer (SSL) connection.
-nosessionreuse 
No Session Reuse
Avoids the reuse of a Secure Sockets Layer (SSL) session ID.
-P password 
Password3
Specify a user password.
-populate 
Fast schema change
Turn off Fast schema change.
-r 
Non-reliable I/O1
Enable buffered I/O to the before-image file.
-requireusername 
Require Username
Require users starting servers of the AdminServer to provide a valid username and password.
-RO 
Read-only media
Open a database for read-only access.
-S { servicename | 
port-number }  
Service name
Identify the service and port number to use on the host machine when connecting to a broker process.
-Sn 
AS/400 server program name
Specify that the Server program on an AS/400 start with an OpenEdge connection request (SNA only).
-ssl 
SSL-based connection
Specifies a Secure Socket Layer connection.
-tstamp 
Time Stamp
Uses time stamp information rather than cyclic redundancy (CRC) to enforce consistency between r-code and a schema.
-trig { dir-name | 
lib-name } 
Trigger location
Identify the directory or library containing the 4GL triggers for a database.
-U userid 
User ID3
Specify the user ID.
1Single-user database connections only; otherwise, use only for server startup.
2UNIX, Windows only.
3Different meaning for non-OpenEdge databases.


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095